Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c719513673b92e53158b0e2a98cf4bb21b28c5d71a0dcddf91c1138ba11e860b

Tx prefix hash: 5277776009697bdacd780e8bb61c2813b92c50880df7bd4e7b450fe93c85f06f
Tx public key: 27ebc4b30c76433ea202caa1073f0bdee9e1ef29c7b251f166ba73f8d22728d6
Timestamp: 1732623798 Timestamp [UCT]: 2024-11-26 12:23:18 Age [y:d:h:m:s]: 00:122:01:26:05
Block: 1162116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87039 RingCT/type: yes/0
Extra: 0127ebc4b30c76433ea202caa1073f0bdee9e1ef29c7b251f166ba73f8d22728d6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac5f29c9a664f3876c18446d4e24f2bf519e6ddbb837a7432e3da0be1518d33 0.600000000000 1647771 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": 1162126, "vin": [ { "gen": { "height": 1162116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac5f29c9a664f3876c18446d4e24f2bf519e6ddbb837a7432e3da0be1518d33" } } ], "extra": [ 1, 39, 235, 196, 179, 12, 118, 67, 62, 162, 2, 202, 161, 7, 63, 11, 222, 233, 225, 239, 41, 199, 178, 81, 241, 102, 186, 115, 248, 210, 39, 40, 214, 2, 17, 0, 0, 0, 6, 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