Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 902d13e69c1bb1f73216828a4730a1907737ac73fbbe4a10cb283fe1d13f6eb2

Tx prefix hash: 45791e408e65b256e699cdab2f8da95599933ceed65c7b5958e056125b6bc9f5
Tx public key: a0ef2a07ba8e86e1d11052fd5ff69801eaeff88af488cdd9b312e20df105b07a
Timestamp: 1673045293 Timestamp [UCT]: 2023-01-06 22:48:13 Age [y:d:h:m:s]: 01:330:10:54:35
Block: 669132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497212 RingCT/type: yes/0
Extra: 01a0ef2a07ba8e86e1d11052fd5ff69801eaeff88af488cdd9b312e20df105b07a02110000000452542ceb000000000000000000

1 output(s) for total of 3.722955735000 dcy

stealth address amount amount idx
00: ac057bee2fea5c43f632b9cfd7a52270c465a456f97f44de445e0eb23cdbf1b7 3.722955735000 1110435 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": 669142, "vin": [ { "gen": { "height": 669132 } } ], "vout": [ { "amount": 3722955735, "target": { "key": "ac057bee2fea5c43f632b9cfd7a52270c465a456f97f44de445e0eb23cdbf1b7" } } ], "extra": [ 1, 160, 239, 42, 7, 186, 142, 134, 225, 209, 16, 82, 253, 95, 246, 152, 1, 234, 239, 248, 138, 244, 136, 205, 217, 179, 18, 226, 13, 241, 5, 176, 122, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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