Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b250178003d5a5f5824e7419d0dd4473ed80e9fd759d290563b8378c9d41588b

Tx prefix hash: c5abc34774f629e5c66acc0ded8277e4af46050079f9dd8ae717d1f1dfd86e0d
Tx public key: 7169c3d8e2ae595ec439844102148194a54b6cc6abacaf2ff51ca385c0fb8df3
Timestamp: 1577144812 Timestamp [UCT]: 2019-12-23 23:46:52 Age [y:d:h:m:s]: 05:313:01:22:27
Block: 30197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371401 RingCT/type: yes/0
Extra: 017169c3d8e2ae595ec439844102148194a54b6cc6abacaf2ff51ca385c0fb8df3021100000021d81c26c0000000000000000000

1 output(s) for total of 487.467499463000 dcy

stealth address amount amount idx
00: 23d9f29c328aae86276f10fba0fb495342076b0c912e85a164e214bd456ca6e8 487.467499463000 49863 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": 30207, "vin": [ { "gen": { "height": 30197 } } ], "vout": [ { "amount": 487467499463, "target": { "key": "23d9f29c328aae86276f10fba0fb495342076b0c912e85a164e214bd456ca6e8" } } ], "extra": [ 1, 113, 105, 195, 216, 226, 174, 89, 94, 196, 57, 132, 65, 2, 20, 129, 148, 165, 75, 108, 198, 171, 172, 175, 47, 245, 28, 163, 133, 192, 251, 141, 243, 2, 17, 0, 0, 0, 33, 216, 28, 38, 192, 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