Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71888ec2f34ebbfe85a47a1a3ddc353051019e071b583770f2c7d7b80255e627

Tx prefix hash: b42f24739c1ccbbc328d1e452e5b2dfbedf22cbb82ec58b0077f4cc071eaccbc
Tx public key: 2d112edfe67a220a299dbbc0530277b5c6d81b1bb57ef8e19f1614752f64f3bf
Timestamp: 1740948055 Timestamp [UCT]: 2025-03-02 20:40:55 Age [y:d:h:m:s]: 00:256:10:58:48
Block: 1230765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181044 RingCT/type: yes/0
Extra: 012d112edfe67a220a299dbbc0530277b5c6d81b1bb57ef8e19f1614752f64f3bf021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8cb3e1af62284f4b0f7fa509b3300ac13a5fdd57686c1df99c6fcdde72bfe9c 0.600000000000 1717664 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": 1230775, "vin": [ { "gen": { "height": 1230765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8cb3e1af62284f4b0f7fa509b3300ac13a5fdd57686c1df99c6fcdde72bfe9c" } } ], "extra": [ 1, 45, 17, 46, 223, 230, 122, 34, 10, 41, 157, 187, 192, 83, 2, 119, 181, 198, 216, 27, 27, 181, 126, 248, 225, 159, 22, 20, 117, 47, 100, 243, 191, 2, 17, 0, 0, 0, 3, 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