Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d9692f43c6cf63b45030c8b4b1587557001f4255133560a0cadb52fb7550f4

Tx prefix hash: 64b7b663382f95e0a2ab7f7128fb410953c43a62bbc43c4b47dbf76205775c1c
Tx public key: b35d6a733e385fc5f23af3c83106e7e6a5880dd1efb3f050002a085a2f81ca7e
Timestamp: 1723528848 Timestamp [UCT]: 2024-08-13 06:00:48 Age [y:d:h:m:s]: 01:086:21:10:13
Block: 1086809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320564 RingCT/type: yes/0
Extra: 01b35d6a733e385fc5f23af3c83106e7e6a5880dd1efb3f050002a085a2f81ca7e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9a8dbd9b47ee2c6ddab7bf3d43230aeb44227ffb91c99ba93ed0502144ca89 0.600000000000 1561408 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": 1086819, "vin": [ { "gen": { "height": 1086809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9a8dbd9b47ee2c6ddab7bf3d43230aeb44227ffb91c99ba93ed0502144ca89" } } ], "extra": [ 1, 179, 93, 106, 115, 62, 56, 95, 197, 242, 58, 243, 200, 49, 6, 231, 230, 165, 136, 13, 209, 239, 179, 240, 80, 0, 42, 8, 90, 47, 129, 202, 126, 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