Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a446720830ef35c5f8173fb10802e741fe86d9fe57e9274a056124a258165ca

Tx prefix hash: 53aebaa306c7553301d98a63aeacefd23b258ff963365dcf21cf456fa8e98d83
Tx public key: eede0a9e60821a217d8d4e4bf34ad453ed3133c7587a4f5ee9bd8af8b8300f69
Timestamp: 1734795173 Timestamp [UCT]: 2024-12-21 15:32:53 Age [y:d:h:m:s]: 00:100:19:11:06
Block: 1180131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71787 RingCT/type: yes/0
Extra: 01eede0a9e60821a217d8d4e4bf34ad453ed3133c7587a4f5ee9bd8af8b8300f69021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 080f1fe4375a55e42f312637bc4f04bc37d5567618efdbd6f2b3d86f1b1a80cb 0.600000000000 1666536 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": 1180141, "vin": [ { "gen": { "height": 1180131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "080f1fe4375a55e42f312637bc4f04bc37d5567618efdbd6f2b3d86f1b1a80cb" } } ], "extra": [ 1, 238, 222, 10, 158, 96, 130, 26, 33, 125, 141, 78, 75, 243, 74, 212, 83, 237, 49, 51, 199, 88, 122, 79, 94, 233, 189, 138, 248, 184, 48, 15, 105, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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