Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5b13093c54aa9c047e51f7f413ea0af6297111bfe1f28ecb16294b3be8f8e9

Tx prefix hash: 620682955e195c81ae2313c8833c78c0c31ebd80c779ef0936891499986b1a82
Tx public key: 9270c51abcecaa733bf854e0c60807b312167bb874f4598218dd2942414c1d7d
Timestamp: 1681479523 Timestamp [UCT]: 2023-04-14 13:38:43 Age [y:d:h:m:s]: 01:284:09:27:54
Block: 738440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464727 RingCT/type: yes/0
Extra: 019270c51abcecaa733bf854e0c60807b312167bb874f4598218dd2942414c1d7d021100000005b3164c24000000000000000000

1 output(s) for total of 2.194026956000 dcy

stealth address amount amount idx
00: 9364df2cfc34bbd43043ab8e2aa82a3f96f288037fe11b445032d129f3e69a1e 2.194026956000 1185127 of 0

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": 738450, "vin": [ { "gen": { "height": 738440 } } ], "vout": [ { "amount": 2194026956, "target": { "key": "9364df2cfc34bbd43043ab8e2aa82a3f96f288037fe11b445032d129f3e69a1e" } } ], "extra": [ 1, 146, 112, 197, 26, 188, 236, 170, 115, 59, 248, 84, 224, 198, 8, 7, 179, 18, 22, 123, 184, 116, 244, 89, 130, 24, 221, 41, 66, 65, 76, 29, 125, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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