Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf1397be017c3fcb9927cfdd6c1b2befd6c259d16a37324498f16fff189641f

Tx prefix hash: aac8d7631f51084924eed7e29e5e37763fb681ef97ef4fb24f4408aba721d18b
Tx public key: cae0d797a83082f3e284a7ead7999f924daaa67e71ac596513c16507d5eaf058
Timestamp: 1730819637 Timestamp [UCT]: 2024-11-05 15:13:57 Age [y:d:h:m:s]: 00:143:13:42:52
Block: 1147166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102440 RingCT/type: yes/0
Extra: 01cae0d797a83082f3e284a7ead7999f924daaa67e71ac596513c16507d5eaf058021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 587f448179e4b9d96c89b568cf392f985a9caae8138c60425e8085396d5c2082 0.600000000000 1631859 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": 1147176, "vin": [ { "gen": { "height": 1147166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "587f448179e4b9d96c89b568cf392f985a9caae8138c60425e8085396d5c2082" } } ], "extra": [ 1, 202, 224, 215, 151, 168, 48, 130, 243, 226, 132, 167, 234, 215, 153, 159, 146, 77, 170, 166, 126, 113, 172, 89, 101, 19, 193, 101, 7, 213, 234, 240, 88, 2, 17, 0, 0, 0, 1, 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