Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f52b9c83a3bc25126f68b431b9c437be0eda48375dfb5cbb639e9191f2fff0d8

Tx prefix hash: f5e50db794f28415644bef0f7d27ae63416dca72318d4163d4c41c7ee7ef7996
Tx public key: bd3277e6d6dbcd0af8b30052150556b18ddea1cff87c5089a4a9c1f14e42cd3d
Timestamp: 1719736728 Timestamp [UCT]: 2024-06-30 08:38:48 Age [y:d:h:m:s]: 00:280:14:46:04
Block: 1055368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200494 RingCT/type: yes/0
Extra: 01bd3277e6d6dbcd0af8b30052150556b18ddea1cff87c5089a4a9c1f14e42cd3d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6567b94e7e5c2402bc7e9a93cc4be9eaec385a685d4bdebb8ce2151b27015e9c 0.600000000000 1525767 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": 1055378, "vin": [ { "gen": { "height": 1055368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6567b94e7e5c2402bc7e9a93cc4be9eaec385a685d4bdebb8ce2151b27015e9c" } } ], "extra": [ 1, 189, 50, 119, 230, 214, 219, 205, 10, 248, 179, 0, 82, 21, 5, 86, 177, 141, 222, 161, 207, 248, 124, 80, 137, 164, 169, 193, 241, 78, 66, 205, 61, 2, 17, 0, 0, 0, 6, 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