Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366f8250e1dfd4e9ebeba17ec1534fea91cb45a0cb120f334706f9426c4da748

Tx prefix hash: e10d667c01c3750660e9d65cbe50018e924cb379ace33b3b0fdb3a452812046f
Tx public key: 5f29037fd0d49d26d99a082174513cbb856623df3a723da819e21148af6140e0
Timestamp: 1574678030 Timestamp [UCT]: 2019-11-25 10:33:50 Age [y:d:h:m:s]: 05:341:14:35:29
Block: 17096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1384502 RingCT/type: yes/0
Extra: 015f29037fd0d49d26d99a082174513cbb856623df3a723da819e21148af6140e0021100000001f95225a5000000000000000000

1 output(s) for total of 538.709626418000 dcy

stealth address amount amount idx
00: c1c28c4d46138e35bff546a6bafc18e9ec566b38ec75bca4605fce725e7e299e 538.709626418000 24466 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": 17106, "vin": [ { "gen": { "height": 17096 } } ], "vout": [ { "amount": 538709626418, "target": { "key": "c1c28c4d46138e35bff546a6bafc18e9ec566b38ec75bca4605fce725e7e299e" } } ], "extra": [ 1, 95, 41, 3, 127, 208, 212, 157, 38, 217, 154, 8, 33, 116, 81, 60, 187, 133, 102, 35, 223, 58, 114, 61, 168, 25, 226, 17, 72, 175, 97, 64, 224, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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