Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25ae87ec78a11d8d886526cab5d33f16177d4c393d746214d5d213308a321d0e

Tx prefix hash: 419768ee92dc5fc62ddaf19ca2d8bb0c8ed272662a001090a3460b660e96f00a
Tx public key: 9f1fd822202af3e9d7773ce9b948398f721b8ab7ab038151aab063254864f410
Timestamp: 1735443637 Timestamp [UCT]: 2024-12-29 03:40:37 Age [y:d:h:m:s]: 00:169:05:24:47
Block: 1185459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120672 RingCT/type: yes/0
Extra: 019f1fd822202af3e9d7773ce9b948398f721b8ab7ab038151aab063254864f410021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a90f254b595794c037b222c2d6c9c6a879f8e4a37f06d6fd09c7ac03fbd0fa6e 0.600000000000 1671930 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": 1185469, "vin": [ { "gen": { "height": 1185459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90f254b595794c037b222c2d6c9c6a879f8e4a37f06d6fd09c7ac03fbd0fa6e" } } ], "extra": [ 1, 159, 31, 216, 34, 32, 42, 243, 233, 215, 119, 60, 233, 185, 72, 57, 143, 114, 27, 138, 183, 171, 3, 129, 81, 170, 176, 99, 37, 72, 100, 244, 16, 2, 17, 0, 0, 0, 2, 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