Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b36a59f08ebb59704b5f6234d46488f7e847e7f4ab365043f55ff4583c066c14

Tx prefix hash: 39cc6b721e069c3df468a558b8f385e575120950aa014c1c7a445722127193c4
Tx public key: f11f8f4eaec63877f5c9a70e3d203bdef62afb0586302bdc250e7a752c40014a
Timestamp: 1725241212 Timestamp [UCT]: 2024-09-02 01:40:12 Age [y:d:h:m:s]: 00:193:23:15:27
Block: 1101009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138487 RingCT/type: yes/0
Extra: 01f11f8f4eaec63877f5c9a70e3d203bdef62afb0586302bdc250e7a752c40014a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45f986195c4230274ab3ee4558a1d50d396df7291426ef5cab7decfa7c3c81d 0.600000000000 1576990 of 15

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": 1101019, "vin": [ { "gen": { "height": 1101009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45f986195c4230274ab3ee4558a1d50d396df7291426ef5cab7decfa7c3c81d" } } ], "extra": [ 1, 241, 31, 143, 78, 174, 198, 56, 119, 245, 201, 167, 14, 61, 32, 59, 222, 246, 42, 251, 5, 134, 48, 43, 220, 37, 14, 122, 117, 44, 64, 1, 74, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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