Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde3137f03b10dde1f620f16b7e76c1bc982f2c04f23280816ad29cc506df135

Tx prefix hash: 4b16ef2dfbdb501fa56463703a8c3cdb1581331c45c1fa8a0fc0cb85ba826b82
Tx public key: ab84cf893d93c716e0f7c3993891fe403c95c783b668d779dd9af6b83e59b836
Timestamp: 1664618770 Timestamp [UCT]: 2022-10-01 10:06:10 Age [y:d:h:m:s]: 02:260:11:20:16
Block: 599539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707667 RingCT/type: yes/0
Extra: 01ab84cf893d93c716e0f7c3993891fe403c95c783b668d779dd9af6b83e59b836021100000002e6d27f9c000000000000000000

1 output(s) for total of 6.331089791000 dcy

stealth address amount amount idx
00: 5e4cdebb20b988a2e798bc472946168b34d15628712e12870f4fdab1b2dfd0eb 6.331089791000 1035450 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": 599549, "vin": [ { "gen": { "height": 599539 } } ], "vout": [ { "amount": 6331089791, "target": { "key": "5e4cdebb20b988a2e798bc472946168b34d15628712e12870f4fdab1b2dfd0eb" } } ], "extra": [ 1, 171, 132, 207, 137, 61, 147, 199, 22, 224, 247, 195, 153, 56, 145, 254, 64, 60, 149, 199, 131, 182, 104, 215, 121, 221, 154, 246, 184, 62, 89, 184, 54, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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