Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d40bd9db2c38d070e35509d9b3f2dc4496c4118e81c80a9b313dd2ad97630ae

Tx prefix hash: 1083f876e279f26c216da6057014de538bcc804913d15b66e5b5398ca2146fa6
Tx public key: 4a143f8f0ab7fa6228f78a18e79e06843841af88036716a7e7e083dba668cc22
Timestamp: 1727310832 Timestamp [UCT]: 2024-09-26 00:33:52 Age [y:d:h:m:s]: 00:148:09:29:04
Block: 1118164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105828 RingCT/type: yes/0
Extra: 014a143f8f0ab7fa6228f78a18e79e06843841af88036716a7e7e083dba668cc22021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b41d8a9aa8ad5a6d4f22d6bd6d7eb69a73b12c0149b7bc99ae0d4c9dc013480f 0.600000000000 1599263 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": 1118174, "vin": [ { "gen": { "height": 1118164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b41d8a9aa8ad5a6d4f22d6bd6d7eb69a73b12c0149b7bc99ae0d4c9dc013480f" } } ], "extra": [ 1, 74, 20, 63, 143, 10, 183, 250, 98, 40, 247, 138, 24, 231, 158, 6, 132, 56, 65, 175, 136, 3, 103, 22, 167, 231, 224, 131, 219, 166, 104, 204, 34, 2, 17, 0, 0, 0, 1, 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