Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fe32518e5c39e8aa670128ae110d5cf229b4ab7c68e0bbe0e614c2169010979

Tx prefix hash: 1ae0373ca408f96525f7702dd3bb7203319242721975133bd411f45fc999d868
Tx public key: 0280e1494f594627234d3fc6224f1331d63f5a13b1d98e6ca4b2b91fca5afb21
Timestamp: 1688618195 Timestamp [UCT]: 2023-07-06 04:36:35 Age [y:d:h:m:s]: 01:287:04:36:05
Block: 797651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466392 RingCT/type: yes/0
Extra: 010280e1494f594627234d3fc6224f1331d63f5a13b1d98e6ca4b2b91fca5afb2102110000000175e3f0e9000000000000000000

1 output(s) for total of 1.396533152000 dcy

stealth address amount amount idx
00: bb6ca1b9b084c4816b371e2140e35494818a19c6e3a0d06004cc2e27c2c1fce1 1.396533152000 1248562 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": 797661, "vin": [ { "gen": { "height": 797651 } } ], "vout": [ { "amount": 1396533152, "target": { "key": "bb6ca1b9b084c4816b371e2140e35494818a19c6e3a0d06004cc2e27c2c1fce1" } } ], "extra": [ 1, 2, 128, 225, 73, 79, 89, 70, 39, 35, 77, 63, 198, 34, 79, 19, 49, 214, 63, 90, 19, 177, 217, 142, 108, 164, 178, 185, 31, 202, 90, 251, 33, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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