Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9314b1f3214a7bc7dd2286de11a9e868f86a616be481d25a6c7bef5aadc9c5f0

Tx prefix hash: 063cd148a82f858c70bfdc6702a1a5f28de25790fc6ce82302aa954ae2a47f10
Tx public key: 483adb47d96d7f00490de949d3f945cfefae5bd86c0e573b5ff16cd2e93351b1
Timestamp: 1706652919 Timestamp [UCT]: 2024-01-30 22:15:19 Age [y:d:h:m:s]: 02:002:20:48:35
Block: 946878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521651 RingCT/type: yes/0
Extra: 01483adb47d96d7f00490de949d3f945cfefae5bd86c0e573b5ff16cd2e93351b102110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f59273b0637cde1ac12e5c81299584b0e003a99bc837cb4476be3cd46a6d95d 0.600000000000 1405220 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": 946888, "vin": [ { "gen": { "height": 946878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f59273b0637cde1ac12e5c81299584b0e003a99bc837cb4476be3cd46a6d95d" } } ], "extra": [ 1, 72, 58, 219, 71, 217, 109, 127, 0, 73, 13, 233, 73, 211, 249, 69, 207, 239, 174, 91, 216, 108, 14, 87, 59, 95, 241, 108, 210, 233, 51, 81, 177, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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