Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 88107aaba5cb275f3ee959398192001ff3966ec5f423eb93b806384ee5aa256d

Tx prefix hash: 5d1e53f07ecbd19535ce6c74dc93ed6f8abe428da7d340f575a89021f2ce74e0
Tx public key: 464f1f43b21803fd0cf6a6b28a1e729f7624b31ee53fe79c7b9fc03a4b54720a
Timestamp: 1635941835 Timestamp [UCT]: 2021-11-03 12:17:15 Age [y:d:h:m:s]: 03:132:00:10:56
Block: 366465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872664 RingCT/type: yes/0
Extra: 01464f1f43b21803fd0cf6a6b28a1e729f7624b31ee53fe79c7b9fc03a4b54720a021100000002f56b629f000000000000000000

1 output(s) for total of 37.476757750000 dcy

stealth address amount amount idx
00: a047cdb5bb0afa94d84e0aebed35d7bfb2b4ca8f53a8791dc49b38d56a02b7b3 37.476757750000 743885 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 366475, "vin": [ { "gen": { "height": 366465 } } ], "vout": [ { "amount": 37476757750, "target": { "key": "a047cdb5bb0afa94d84e0aebed35d7bfb2b4ca8f53a8791dc49b38d56a02b7b3" } } ], "extra": [ 1, 70, 79, 31, 67, 178, 24, 3, 253, 12, 246, 166, 178, 138, 30, 114, 159, 118, 36, 179, 30, 229, 63, 231, 156, 123, 159, 192, 58, 75, 84, 114, 10, 2, 17, 0, 0, 0, 2, 245, 107, 98, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8