Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b79dbdc9598b1cfee8fe6a3fd8c79c495f84cf649a157093c655224cdc25b8f7

Tx prefix hash: 9e95d18337c78f35b1c3fcf2e61fca417b222e89131497369d090d8e3f7a4345
Tx public key: fc212a0a1cac001bde37df8da05326148bff00a2a707c5c85d4de2d5ff0bbb80
Timestamp: 1731172389 Timestamp [UCT]: 2024-11-09 17:13:09 Age [y:d:h:m:s]: 00:131:05:30:30
Block: 1150100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93624 RingCT/type: yes/0
Extra: 01fc212a0a1cac001bde37df8da05326148bff00a2a707c5c85d4de2d5ff0bbb80021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad9e93bbcb5a243dd5eeedb9bbcaf9330549c70f3497ace3e9d3b3a99d70211 0.600000000000 1635307 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": 1150110, "vin": [ { "gen": { "height": 1150100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad9e93bbcb5a243dd5eeedb9bbcaf9330549c70f3497ace3e9d3b3a99d70211" } } ], "extra": [ 1, 252, 33, 42, 10, 28, 172, 0, 27, 222, 55, 223, 141, 160, 83, 38, 20, 139, 255, 0, 162, 167, 7, 197, 200, 93, 77, 226, 213, 255, 11, 187, 128, 2, 17, 0, 0, 0, 5, 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