Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31848af1a77e10918672dea4c558eb69411229bc38b96cb2391057c11b08731

Tx prefix hash: 7768b3f3e05d8c9d21d0c3b0cc5f754b5b74fcd15b42fa28d6433d2dcbf0dbd0
Tx public key: cd26d64780c0abb53a552169193abc2baa828575a7fa2ae2470d55a2581d13f8
Timestamp: 1733634674 Timestamp [UCT]: 2024-12-08 05:11:14 Age [y:d:h:m:s]: 00:110:00:13:26
Block: 1170495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78409 RingCT/type: yes/0
Extra: 01cd26d64780c0abb53a552169193abc2baa828575a7fa2ae2470d55a2581d13f8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b37e31ba35c053625d3e9e994ff635613a9981bb182ba40d83f0a824266e4d 0.600000000000 1656226 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": 1170505, "vin": [ { "gen": { "height": 1170495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b37e31ba35c053625d3e9e994ff635613a9981bb182ba40d83f0a824266e4d" } } ], "extra": [ 1, 205, 38, 214, 71, 128, 192, 171, 181, 58, 85, 33, 105, 25, 58, 188, 43, 170, 130, 133, 117, 167, 250, 42, 226, 71, 13, 85, 162, 88, 29, 19, 248, 2, 17, 0, 0, 0, 4, 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