Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c365117b493241ebfd59613c1cd47bfd071490819a746e66784f9ca90b15226

Tx prefix hash: fc5da17639c03f3b1efa3208d8e595eea9e8a55bc19d6ea67241690c142fb933
Tx public key: f215d524e07e18d56b4c94f60501976b7ddb3b867eb442df31c4d136261015e4
Timestamp: 1720734425 Timestamp [UCT]: 2024-07-11 21:47:05 Age [y:d:h:m:s]: 00:263:12:02:43
Block: 1063652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188237 RingCT/type: yes/0
Extra: 01f215d524e07e18d56b4c94f60501976b7ddb3b867eb442df31c4d136261015e402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45947026debca2d2f9f6b2f573e5f49edb4c1196e8702c07cfb19e18d5afb830 0.600000000000 1534169 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": 1063662, "vin": [ { "gen": { "height": 1063652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45947026debca2d2f9f6b2f573e5f49edb4c1196e8702c07cfb19e18d5afb830" } } ], "extra": [ 1, 242, 21, 213, 36, 224, 126, 24, 213, 107, 76, 148, 246, 5, 1, 151, 107, 125, 219, 59, 134, 126, 180, 66, 223, 49, 196, 209, 54, 38, 16, 21, 228, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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