Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99f5192a483d475c3113e627e2a8e4ac1a659e55508341ef655a3d0d65f4f0e0

Tx prefix hash: 80f4fc740397c13be0f757db7557258a870fdfc9d942beb7ee7eb3e582390885
Tx public key: 34084d2ddd9eae80e86bc28ad63ccd21133141b7f5bc684c68ac62d66f86be68
Timestamp: 1728623274 Timestamp [UCT]: 2024-10-11 05:07:54 Age [y:d:h:m:s]: 00:168:03:29:44
Block: 1129041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119957 RingCT/type: yes/0
Extra: 0134084d2ddd9eae80e86bc28ad63ccd21133141b7f5bc684c68ac62d66f86be68021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1f93936d9e797015bbc956c517f2c7a0a3f3bfee188af463362b2446aa8a04e 0.600000000000 1611864 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": 1129051, "vin": [ { "gen": { "height": 1129041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1f93936d9e797015bbc956c517f2c7a0a3f3bfee188af463362b2446aa8a04e" } } ], "extra": [ 1, 52, 8, 77, 45, 221, 158, 174, 128, 232, 107, 194, 138, 214, 60, 205, 33, 19, 49, 65, 183, 245, 188, 104, 76, 104, 172, 98, 214, 111, 134, 190, 104, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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